Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-39391 | SRG-OS-000109-ESXI5 | SV-51249r2_rule | Medium |
Description |
---|
Even though communications are encrypted, an additional layer of security may be gained by extending the policy of not logging directly on as root. In addition, logging in with a user-specific account preserves the audit trail. |
STIG | Date |
---|---|
VMware ESXi Server 5.0 Security Technical Implementation Guide | 2017-01-06 |
Check Text ( C-46665r4_chk ) |
---|
For ESXi hosts that are not managed by a vCenter Server, this check is not applicable. Disable lock down mode. Enable the ESXi Shell. Execute the following command(s): # grep PermitRootLogin /etc/ssh/sshd_config If "PermitRootLogin" is set to "yes", this is a finding. Re-enable lock down mode. |
Fix Text (F-44404r3_fix) |
---|
This step assumes that root access to the system is available via the vSphere Client/vCenter Server, local availability via the DCUI, or that remote systems are accessible at the remote site via touch labor by an authorized (root) user. Disable lock down mode. Enable the ESXi Shell. Execute the following command(s): # vi /etc/ssh/sshd_config Add/modify the attribute line entry to the following (quotes for emphasis only): "PermitRootLogin no" Re-enable lock down mode. |